Skip to content

release: v1.5.1 — Marketplace recovery republish of v1.5.0#48

Merged
dmartinochoa merged 1 commit into
mainfrom
release/v1.5.1
May 27, 2026
Merged

release: v1.5.1 — Marketplace recovery republish of v1.5.0#48
dmartinochoa merged 1 commit into
mainfrom
release/v1.5.1

Conversation

@dmartinochoa
Copy link
Copy Markdown
Member

Summary

  • Marketplace recovery republish. The v1.5.0 tag push hit a 3-minute Microsoft-side timeout on _apis/gallery during the Marketplace publish step; vsce publish returned non-zero before the upload committed. Open VSX and the GitHub release for v1.5.0 both shipped fine (workflow log: 🚀 Published greylag-ci.pipeline-check v1.5.0). Only Marketplace missed it — users there are still on 1.1.0.
  • No source changes between v1.5.0 and v1.5.1 — tag exists solely to re-fire the publish pipeline. Mirrors the existing v1.0.3 pattern (recovery for v1.0.2 OVSX 405).
  • Net effect post-merge + tag: Marketplace jumps 1.1.0 → 1.5.1 (skipping 1.5.0, which was never there), Open VSX goes 1.5.0 → 1.5.1 (no functional diff).

Verification

  • npm run typecheck — clean
  • npm test — 391/391 pass
  • npm run lint — clean
  • npm run vscode:prepublish — bundle 376.3 KB
  • npm run smoke — bundle exports activate/deactivate
  • npm audit --omit=dev --audit-level=high — 0 vulnerabilities
  • GitHub release for v1.5.0 confirmed alive (vsix + SBOM attached)
  • Open VSX /versions endpoint confirms 1.5.0 is published
  • Marketplace extensionquery confirms latest there is still 1.1.0
  • Tag v1.5.1 after merge to retry the Marketplace publish

🤖 Generated with Claude Code

VS Code Marketplace publish step on the v1.5.0 tag push timed out on
`_apis/gallery` (3-min hang on Microsoft's gallery API) and `vsce
publish` returned non-zero before the upload committed. Open VSX
and the GitHub release for v1.5.0 both shipped fine — only the
Marketplace missed it. This tag exists solely to re-fire the
publish pipeline so Marketplace catches up.

No source changes between v1.5.0 and v1.5.1. Mirrors the existing
v1.0.3 recovery pattern (v1.0.2 OVSX 405).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 27, 2026

Warning

Review limit reached

@dmartinochoa, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 10 minutes and 55 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2dd7065a-7c7b-4d75-8316-97afafba8e57

📥 Commits

Reviewing files that changed from the base of the PR and between 78aa6c5 and 258f8cd.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • CHANGELOG.md
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/v1.5.1

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@dmartinochoa dmartinochoa merged commit 19261f0 into main May 27, 2026
12 checks passed
@dmartinochoa dmartinochoa deleted the release/v1.5.1 branch May 27, 2026 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant